Well, 3 days later, no more weird out of frame picture! I think I can safely say that it solved it. Thanks again @mitu !

@mitu : Thanks, makes perfect sense. I suspected it was something like that.

Thanks for the tip @dankcushions. This was driving me insane. I'll update from source when Mario Kart 64 misbehaves from now on :)

@Affleck001 Exit Emulationstation and then rename the one that does not have the images, then reboot and check if images are working ok.

@RetroFreak89 One way to make sure that the extra space really doesn't contain any data is to shrink the second partition on the original sd card by 1 GB. But since this partition contains a Linux file system, you need a Linux partitioner like GParted for that (or a Windows partitioner that can shrink Linux partitions with the file system ext4 on them, if such a tool exists).

If you're not using Linux anyway, you could use the GParted Live image that boots from a CD or a USB medium into a graphical Linux system with GParted pre-installed.

After shrinking the second partition on your card, you would make a new image that has guaranteed no data in its last 1 GB and should be safe to write to your new card. After confirming that the new card works and has all the data on it, you could then grow its second partition with GParted to the maximum size of the new card.

That's a good idea. As you mentioned on another post, this could make it much easier to make themes compatible with the 4:3 format.

Cheers,

The same also applies for hard drives. You will never get what the actual size is quoted due to filesystem overheads and lose even more space depending what filesystem you format them to. Some take more space than others, some are very efficient filesystems, some are not

@omgmog Cool app! ;)

This won't work.
The vfat boot partition should contain only boot files, and the linux OS has to run on a linux FS type. Period.

What you could do is shrinking the ext partition, then create a new one, format it VFAT and mount it on /home/pi/roms, but this would cause issues with simlink ans so, and it's really FAR from being straightforward.

SMB and USB should not be so slow, especially if you only need 2Gb, and I would recommand to use them.

@herb_fargus said in Make backup image:

@inunotaishou sharing ROMs is against the forum rules. And even if your image didn't have ROMs it's incredibly reckless to share an image with all your configs which likely include your credentials for wifi access among other things.

Follow the available guides. Having other people do things for you does nobody any good.

So..... Where are the working guides you talk about?

Tried this one, and failed
Tried this one first, failed
I really wanted this one to work, but it kept breaking at the end

It's a good thing there are no ROMs on that image. My wifi credentials might be on there. The only thing I did to that image was run my publically available PiStation 2 setup script and configure the PS2 controllers before I made the image. I think I use that password on some throw away email accounts and pokemon games that I don't even know the account names to.

Thanks @funkybunch great info as always :)

I beat the 'white flash' anyhow.....I just created extra image elements and resized the png bg to 1280x720 (luckily it was a pixel background) and it works flawlessly now :)

Thanks for the heads up on ES, I might start a new topic regarding the change of language in ES (xxx games available).

@FlavioBello11

The size depends in how many quality / filesize you want. Emulationstation will scale the image to fit screen so you can use any resolution you like.

If you want to make a theme for 16:9 screen then do your bacground at a 16:9 resolution, and if you want to make your theme for 4:3 screens then use a 4:3 resolution.

List of common resolutions: https://en.wikipedia.org/wiki/List_of_common_resolutions

I recommend to you 1920x1080 or 1280x720 for 16:9 and 1024x768 or 800x600 for 4:3.

Regards.